
I see one of the greatest challenges in compiling AppleSoft is the number format. AppleSoft wants to do everything in floating point. As there wasnt much benefit in defining integer variables (except in arrays), it will be hard to identify which variables can be handled with integer values. This is one of the main reasons AppleSoft runs so slow. An assembly language programmer will choose the best sized variable width and use appropriate routines for manipulating them. It will be difficult at best to come within 10% of that with compiled AppleSoft. If youre only looking to compile your own code, perhaps overriding the variable type with integer (and even byte -  you would have to make something up) sized identifiers would give your compiler enough isight into the best code to generate.


Figure that out and you have a winner.

DAVE